EF 230 Spring, 2014 Feedback

Please take a few minutes and give us feedback on the class. Your constructive comments are invaluable to us in helping improve the class each semester. You will receive extra credit for completing this form. Thanks.

Labs

Rate the overall quality of the EF 230 class.

15% (17/115) Very good (1) 52% (60/115) Good (2) 23% (27/115) Average (3) 10% (11/115) Marginal (4) 0% (0/115) Poor (5) 0% (0/115) N/A (0) Avg: 2.28, NZAvg: 2.28, sum=262, cnt=115, nzcnt=115

General comments/suggestions about this class.

211.  For a two hour class, the workload was extremely heavy. 212.  This class was a great way to learn a decent amount about basic programming and problem solving. 214.  I like the set-up of the class; I think it was the best way of working with MATLAB by going through the lab and examples then working on homework when there was time at the end. 215.  I learned some really useful info 216.  More class examples, more working examples on your own. 217.  I thought it was hard some weeks, but it was good overall. 218.  I think I struggle with MATLAB, because I have never really had that much interest in computer coding. I think the class incorporated some cool features of MATLAB that I never thought a computer could do. I cannot imagine what other crazy things this program can do considering we have just scraped the surface. 219.  Was really helpful in learning MATLAB. Will be useful later on. 222.  The labs and projects synced up fairly well. But there were definitely skills necessary for the projects that were not covered in labs, or needed some special attention that was not explained. 223.  Overall, this was probably one of the most useful general engineering courses that I have taken so far due to the fact that the majority of our engineering related "technical" work/computations in our career will be computational. Even if I do not ever end up using matlab again (not likely), I will at least have an introduction to solving problems using computational programming. 224.  At times this class takes an exorbitant amount of time, and at other points takes little time. If the workload, specifically projects, could be more spread out so that the amount of work were more even, that would be beneficial. Other than that, generally what is covered is a fair amount. 225.  Much easier than CS102. 226.  It's been a blast. 227.  I personally hate how this and 105 class is set up. Its hard for me to follow what the TAs are doing and the labs seems to not give enough info to help me with the homework. How am I suppose to know how to do some of the code if you guys never even talk about it or put it on the labs?? 228.  Cut back on the project maybe. I thought that the projects were good, but with the amount of them and the difficulty, along with the homeworks for the class, they took up a lot of time for just this class. Also I thought Zyante was rather helpful, it helped me to understand why certain things were used in MATLAB, rather than just using them cause I saw the TA's do it. 229.  The course as a whole was quite difficult and time consuming. I don't feel that adequate time was allotted to develop the depth of skill expected for much of the work in this course. Personally, I felt that Zyante was a great waste of time. It would have been better to have used that time to practice in the actual matlab program rather than reading or inputting into the Zyante program. 230.  I heard that this class was very difficult, and yet it is, however the TA's taught the material very well and helped me learn. 232.  Possibly cover less material and ensure students are learning the material instead of just getting a grade. 233.  Lots of work, but they help you a lot. 234.  This class seems to be improving a lot, compared to when some of my friends took it a few years ago. TA's still could improve with explaining how to think through writing code. 236.  First, this class needs to be AT LEAST 3 credit hours. I have put in more than 2 hours worth of work, and more than some of my other 3 hour engineering classes. Maybe think about making it two semesters. The complexity of some of the information is hard to grasp in a semester, especially with limited TAs and limited one-on-one time. 237.  n/a 238.  The project work takes up so much time and the multiple choice in the tests aren't super important. 239.  It is poorly set up even for a programming class. I have had people look over the class that taught similar classes at other colleges and they were very taken aback at how it was set up and agreed it was not the best set up. 240.  Projects were tough but manageable with time. Also, the homeworks were set up well and helpful for exams. 241.  Its kind of hard to comprehend and type at the same time. 243.  This class is good and I learned a lot, BUT THIS IS NOT A 2 HOUR CLASS. Apparently you guys hear this every year, but I am strongly suggesting you start listening. I learned a ton, but I spent entirely way too much time on the 4 projects we were assigned. 4 projects? I put in twice the work in this course that I would put in a 5 hour lab easy. Don't get me wrong, this class has great teachers and great content, BUT please just actually listen to your students. Let them have a voice and significantly the projects. Change that and you'll get perfect scores, and students that are happy to learn, not aggravated and frustrated. 245.  The material is hard to understand when it is gone over so fast during class. 246.  This class is very informative. Too informative. There is just way too much stuff covered by a 2 hour class. I spend more time on this class a week than any other class I ever have. I know it is important to cover all this material, but this should definitely be at least a 3 hour class. 248.  Requires more out of class work than should be applicable for a 2 credit hour class. 249.  It was a good introduction to a coding language. I feel much more confident about coding than I did in the fall. 250.  The number of credit hours earned does not match the amount of effort required by the classwork. I spend a similar amount of time on my two honors 4 credit hour classes as on this one. 252.  The class was very good and taught very well. 253.  I struggle with MATLAB ever since the EF 105 class, but the TAs (Myles and Jake) that I had this semester were excellent (much better than the EF 105 TAs). It wasn't easy for me to learn, but they tried their hardest to help explain things to me and everyone else in the class. 254.  Just take more time to go over certain topics rather than just zooming threw them. 255.  My second time in this class was a much more pleasant experience. I actually learned this time because i had a much better TA. 256.  I think the class as a whole runs smoothly. I wish the projects were a bit simpler. However, The help sessions were great and there was no excuse for not completing them. I would also recommend some type of review sessions before the test. 257.  Pretty difficult if you're not into coding. 258.  I enjoyed the class. A lot of people complain about the time required to complete the projects...maybe they should change their major. 259.  Very easy to understand the concepts and the TAs did an excellent job of teaching. 260.  I didn't really see a point to this class when I first got in it, and I still don't see a huge use for it, but I understand why we had to take the class. 262.  I suggest that all exams should be in the short answer format, instead of having a portion where code is turned in. It makes the exam completeable during the time table and still shows how well a student can code. 263.  Kinda feels like we rushed through some things and then had time to spare with others. I would of like to be able to have more classroom time to go over the most important things. 264.  felt like we were rushed at times 267.  I think it was an awful lot of work for a two hour class. We are in class for the same amount of time and have more projects than a 2 hour class would require. Make it a 3 hour or lose some of the projects. 268.  Explanations could be better. Going into detail similar to homework and exams would be smart. 269.  Felt like the class was very helpful in teaching us the basics and usefulness of matlab. I do feel that projects 2 and 3 were too difficult however and required way too much work, especially for students with other hard classes 270.  The one issue I had was the fact that I spent more time on this class than on any other of my classes because of the projects, while I feel like less time should be spent on this course considering it is a two hour course and most of my others are three hours and one four hour. 271.  This class is a little rough if you aren't paying attention but is overall a well planned class. 272.  EF 230 is a very interesting class that teaches young engineers how to make problem solving more efficient and easier. I feel as if a textbook should be required for this class or a more detailed side document in our instructors words. Many of us really enjoy the GA's teaching style but it is often taught based off of there extensive prior knowledge. The fault comes in is when we don't easy access to them (at home) and we google things, its kind of foreign due to it not being the teaching style we are used to. Solid class, just a bit more detail in my opinion. 273.  Requires way too much outside work for a two hour class. Spent more time on projects/homework in this than my 4 hour credit class. 275.  Took a very long time to get our first test graded and back. Also, the workbook at the beginning of the class was not helpful. Also, too much work for a 2 hour credit class. Three projects is plenty for the class. The final project is not needed. Also, three tests including the final is perfect. 276.  more in-depth explanations of matlab functions and syntax and alternate uses for functions 277.  Projects were HARD, very time consuming 278.  Well structured class. Would have liked a more in depth introduction to MATLAB, being a student who had never used it before. 279.  Large amount of work for a 2 hour credit course. I learned a hell of alot about matlab though. Cool projects and challenging. 280.  Nupe. 281.  Good class. 282.  This class was mostly a nightmare, certainly my least favorite class in 6 semesters at UT. At its worst, this class seriously had me contemplating not only dropping out of engineering but college all together. I felt like I was a first grader being asked to do Calculus III level work when it came to projects. Homeworks were more reasonable in their expectations and applying lessons from class. I have ended up gaining some working knowledge of Matlab by the end of this course, but it took the essential tutoring of a computer science major friend of mine to gain this and to stand any hope of completing the projects. 284.  it was a good class for learning how computer coding works 285.  Class was pretty tough but overall good. The first test was pretty hard, but I think that was understood by everyone afterwards. The second test was a very good test I believe. Projects were pretty tough, but doable. 286.  This class was influential in learning essential MATLAB skills. I really learned a lot however I felt like the classes and review sessions were too large. When I needed help it took at least 10 minutes to be helped, which is not bad but more individual attention would be better for this class. After all, it's not manual labor, its just figuring out code and syntax. 287.  All of the projects relied on how much the TA's helped. The first test was way too hard. 289.  I was not a big fan of zyante. Especially the frequency with which their answers would have misspellings which made it nearly impossible to get the correct answer without checking. 290.  Zyante was ok, but not the most beneficial. Lectures were pretty good, Matt and Miles did a good job teaching the content and answering questions. The projects were a really tough if you couldn't make it to the help sessions. 291.  Its as good as it is going to get for a computer coding class. There isn't much more you guys can do as far as teaching, because it is a subject that you have to practice. So overall no suggestions. 292.  The tests are pretty hard, and I think that we should have been allowed to use our notes for the multiple choice. 294.  fair difficulty/ work load 296.  Ask for you money back on the zyante software. 297.  I really enjoyed this class. 298.  I felt the first project was very useful. I was able to complete the first project without help. It took me along time to complete the project, but upon completion I felt like I had learned a lot. The second and third projects were not as effective in my mind. I was unable to accomplish much without attending multiple help sessions. I felt the projects were not effective at building my programing skills. I would suggest making the projects smaller and having more of them. This would allow programming skills to build through more of a progression. I had no programming experience before this class, so that could be a major reason as to why I struggled with projects 2 and 3. 299.  I think that if a professor was more involved, possibly attended one class a week for a half hour or so the class would be a bit less confusing. Not that the TA's do a bad job, but they obviously are do not have the pedigree of a professor. It would be more helpful and the class would definitelty improve with another set of experienced eyes watching over it. At times it was confusing. Could've used more Zyante. 300.  Great class. Some classes that don't have a lot of material feel like slightly useless. 301.  All of the labs were pretty helpful, but the Zyante assignments were a little weird to do. They also didn't seem as helpful as the instructors would have been on the same topics. 302.  The TA's could have presented the material more clearly, but basically learning code is up to the student. It would have been super helpful for Professor Schleter to have presented the concept of functions in the beginning because basically everything was built on top of that, and maybe he could have presented the more complicated concepts. It's way easier to follow him than any of the TA's. I understand though that this might not be feasible. 303.  I liked how we got to work on the 3rd project in class by outlining it in a series of steps. I think that the 2nd project should have been like that also, so the students could have gotten a better understanding of how to approach the project. 305.  I think the labs are set up well for you to learn the program. 306.  The projects were difficult but there was good help and the ta's could help with issues. 309.  I don't like how the projects are graded. I got counted of for not putting a title and time on my graph for the third project and that was not included in the project guidelines. Something similar happened on the plotting project, too. 310.  I have a much better understanding of Matlab now. 311.  This class is only two credit hours but it requires way more time to do the homework and projects. Everything we do in this class is time consuming and the lectures are pretty vague. Even though the TA's are willing to help with whatever we need, this class is hard to manage alone. 312.  The projects are always daunting to me. 313.  This could probably be made into an online class it seems. The video lecture format would work better, with discussion boards for questions 314.  I enjoyed the class and definitely felt I learnt more about MATLAB than in EF150. 315.  The class was very unorganized and the workload was a lot more than a two hour class should should have. 316.  It was a lot of work for 2 credits, but it did greatly expand my understanding of Matlab. 318.  Very good at introducing some finer points of matlab. 319.  The rhetoric is really difficult to understand. This class is a class about matlab, but every session touches on many different conceptual topics. This obviously cannot be helped, but the fact is students will be trying to learn what the concept is as well as learning the code at the same time. Its a cumbersome juggle of information and there's no easy way to go about learning it if you don't already have a good grasp of the fundamental concept. 320.  A lot of material to cover. The work load is not a 2 credit hour class. 321.  It should not be a 2 hour class- It's way too involved and waaay too much work for 2 credit hours. Also, a textbook with step by step examples and explanations would have been nice. It's hard to rely on class examples when there are so many different ways to use commands and everyone has personal preference. 322.  I wish the beginning of the class was sped up a bit while more time was spent focusing on the later ideas such as image and sound ussage. 323.  cut out zyante 324.  Can be improved in the area of communicating the information. 325.  The class overall gave me mixed feelings. Some aspects were awesome while others made me dread the class. The class itself was very inconsistent in the time that it desired from you, so this cause some weeks to be particularly more trouble some than the should have been for a 2 hour class. Some of the projects ended up taking 15-20 hours to do, and it would have been nice to know this during midterms so I could have planned accordingly. After the first time or two you learn, but still was a big wake up call. On the other hand, the TA's were great and were always available for help when needed.

Matt Price

Rate the overall quality of your interaction with Matt Price. If you didn't have any interaction with this person, use N/A.

40% (46/115) Very good (1) 26% (30/115) Good (2) 6% (7/115) Average (3) 0% (0/115) Marginal (4) 0% (0/115) Poor (5) 28% (32/115) N/A (0) Avg: 1.10, NZAvg: 1.53, sum=127, cnt=115, nzcnt=83

Rate the quality of Matt Price's presentation and explanation of the material. If this person never presented for your class, use N/A.

31% (36/115) Very good (1) 27% (31/115) Good (2) 1% (1/115) Average (3) 0% (0/115) Marginal (4) 0% (0/115) Poor (5) 41% (47/115) N/A (0) Avg: 0.88, NZAvg: 1.49, sum=101, cnt=115, nzcnt=68

Specific comments/suggestions about Matt Price (optional)

215.  He was aware of the material presented and although he isn't my T.A. he was very helpful at help sessions 218.  He was always very helpful and enthusiastic during the help sessions. I like the way he explains things also. 221.  Matt was very helpful during project sessions and although I did not have him as a TA for my class, he seemed to know the subject material very well and was able to convey it in a very helpful manner. 222.  Matt had a tendency to use code that we had not covered and/or was not the most effecient means of performing the task. 228.  He wasn't one of the TA's for my section but he did help me in one of the help sessions for our project and he was very helpful and explained the solution to my problem very well. 232.  Very Helpful! 233.  Good 236.  I went to a help session for project 2 and I sat there with my hand up for an hour (before finally leaving) because he was the TA for that session and was only helping people in his section (not paying attention to the order of people with questions). He was able to help me during a help session for project 3 and was very helpful then. 241.  N/A 244.  I didn't have him in my lab but he helped me greatly in many a help sesh. Great guy and great T.A. 249.  I only talked to him about code once. He pushed me in the right direction (Sort of). 250.  Very personable and constructive in his criticism. 253.  N/A 262.  Matt does a great job explaining to students how to code during projects. He actually cares if the students learn and is very dedicated, he's willing to stay extra time as well. 263.  Really tries to help out whenever he can. 264.  He was very good at making sure you knew what to do. 267.  Matt was very helpful in lecture and in help sessions. 270.  Seems to know what he's doing but also not as knowledgeable as Jake on the subject (understandable). 272.  Matt has a unorthodox problem solving style that is interesting to hear to get an alternative explanation or understanding when learning code. 273.  Great TA and great guy. Excellent at explaining material and offers great help. 274.  Always willing to help. Pretty nice guy. Good job overall. 275.  Matt was very helpful at explaining how matlab code works. Cares about how the students do in the class. 282.  Very knowledgeable and overly willing to help. Matt was great with offering detailed, clear explanations and guidance when asked. Overall, as good a TA for this course as one could hope for. 283.  Good answers and presentations. 285.  Matt was great and very helpful. 286.  Good guy, really seemed like he cared and wanted to see us do well. Always willing to help out. 287.  Very helpful 288.  Matt is an excellent teacher. He was always willing to help. 289.  His enthusiasm helps make the class engaging. He also does an excellent job explaining the material. 290.  Did a great job lecturing and teaching the material. 292.  Matt's really nice. Although he doesn't know how to spell the word "initial." He always spells it "inital" and that really bothers me. But he's really helpful and knowledgeable! 297.  He's a good teacher. He gives good explanations. 299.  Matt was very helpful and very personable, and his experience with matlab was above average. 302.  He was always ready to help give direction when working on projects. Might be more helpful if he was more specific, but I understand that he's not just going to write people's code for them. 312.  He seemed like he really wanted us to learn this. He'd tell us to pay attention to specific parts that he knew we'd need to know later. He's a real nice guy. 316.  Matt was very helpful, and I enjoyed having him as my TA. He also went out of his way to meet outside of class for project help. 319.  Guy loves matlab. Delivery of information could use work. 320.  Knew what he was doing and was very helpful 321.  Matt is extremely helpful in and out of class and is always ready to answer questions. His explanations sometimes can be a little unclear. 323.  really nice guy 325.  Matt is really cool and was always helpful. His " bedside manner" I guess was a little bit better the the other TA's. So even after not having done it before he did well and helped me out more than he knows. I owe a beer.

Jake Brisby

Rate the overall quality of your interaction with Jake Brisby. If you didn't have any interaction with this person, use N/A.

46% (53/115) Very good (1) 39% (45/115) Good (2) 6% (7/115) Average (3) 1% (1/115) Marginal (4) 0% (0/115) Poor (5) 8% (9/115) N/A (0) Avg: 1.46, NZAvg: 1.58, sum=168, cnt=115, nzcnt=106

Rate the quality of Jake Brisby's presentation and explanation of the material. If this person never presented for your class, use N/A.

49% (56/115) Very good (1) 30% (35/115) Good (2) 7% (8/115) Average (3) 1% (1/115) Marginal (4) 0% (0/115) Poor (5) 13% (15/115) N/A (0) Avg: 1.34, NZAvg: 1.54, sum=154, cnt=115, nzcnt=100

Specific comments/suggestions about Jake Brisby (optional)

215.  Always willing to help me out when I had trouble 218.  He is always nice and helpful. He is also good at answering questions and looking at code to find mistakes. 220.  Super helpful and nice 228.  Jake was kind of the "run the computer TA" for our section, but when he did interject he was pretty good at breaking things down and explaining concepts. 232.  Good. 233.  He is very helpful. 234.  He's forgotten what it's like to be an undergraduate student, especially a sophomore. 236.  Didn't do much teaching, mostly did the computer work during class. But he was very helpful one on one. 243.  He's the man. Very smart. Helped me with any problem I had and explained it well. 244.  Great dude, engineer, and T.A. Very, very helpful even though we complained and bugged him ha. 245.  Good attitude 246.  Very informative in his instructions. 247.  Thanks you all your input throughout the semester 248.  Good class presentation 249.  The TA of my lab section. Explained topics very well, easy to understand. 253.  Jake is very nice, helpful, and funny. He was always willing to help. Very nice guy. 255.  Jake did a good job presenting the material. He was also very helpful with his explanations. 256.  Very helpful, handles the stress of a hands on class well 258.  Great TA. 262.  He is much better of a lecturer than a tutor for the specific projects. 263.  Very smart and worked hard to try to dumb things down for us. 267.  Jake was very helpful in teaching and helping me. 269.  Great TA and very willing to help 270.  Knows what he's doing. 272.  Jake is like the Master Yoda of the EF230 crew. Nothing he does not know there is. 274.  Great TA. Probably the most help I've ever had from a TA in any course. Needs a raise. 275.  Jake was also very helpful at explaining how matlab code works. Cares about how the students do in the class. 282.  Also super knowledgeable and helpful. He was great in class with explanations and made things as clear as they could be. 283.  Seemed very knowledgeable in the help sessions. 285.  Helped me with projects and was really good. 286.  Very good presenter but he was very relaxed and almost did not seem to care to help the students at some points. 287.  Very helpful 288.  Jake is really good at explaining things. 292.  Jake's really nice. 299.  My only interaction with Jake was in a review session for exam 2, but he did a good job in that session. 302.  He was always helpful and willing to give advice for projects. 312.  He popped in and out of our section a few times, and he always had such good tips to give out. 316.  Jake was also very helpful and always got back to me on emails quickly. 319.  Knows his stuff and knows how to get it across to us. 320.  Knew what he was doing and was very helpful. 321.  Jake obviously know what he is doing, but assumes the rest of us do too. He can be slightly condescending and almost sarcastic when answering questions he believes you should know the answer to. 323.  very good helper 325.  While I didn't interact with him as much, you knew he knew his shit. He wasn't as out going as Matt, but was still really cool and was who you went to with the particular tricky problems. He rarely got stumped.

Myles Smith

Rate the overall quality of your interaction with Myles Smith. If you didn't have any interaction with this person, use N/A.

49% (56/115) Very good (1) 29% (33/115) Good (2) 4% (5/115) Average (3) 0% (0/115) Marginal (4) 0% (0/115) Poor (5) 18% (21/115) N/A (0) Avg: 1.19, NZAvg: 1.46, sum=137, cnt=115, nzcnt=94

Rate the quality of Myles Smith's presentation and explanation of the material. If this person never presented for your class, use N/A.

50% (57/115) Very good (1) 22% (25/115) Good (2) 6% (7/115) Average (3) 0% (0/115) Marginal (4) 0% (0/115) Poor (5) 23% (26/115) N/A (0) Avg: 1.11, NZAvg: 1.44, sum=128, cnt=115, nzcnt=89

Specific comments/suggestions about Myles Smith (optional)

215.  Always willing to help me out when I had trouble 220.  Super helpful and nice 225.  He is wearing the same shirt in class today (4/22) as he was in that picture. 228.  Myles was the main presenter for our section, over all I would say that he did a very good job. The only suggestion that I would have is that sometimes, on the more difficult concepts of MATLAB, he would just kind of speed through them and not really go in depth in explaining them. However, I do realize that there was a time constraint for the class, so that also could have had something to do with it. 232.  N/A 233.  He is also very helpful. 236.  Very helpful one on one. Not that good at explaining things when teaching to the class, but explains things better one on one. 243.  Myles is great as well. He always had a firm understanding of the material, and could always help if any questions were asked. 244.  Pretty much identical to what I said about Jake. He is a great dude and deserves the best evaluation I can give him. 245.  very helpful 246.  His instructions are the clearest of all the TA's and he is the most helpful. 247.  Excellent presentations! 248.  Very helpful 249.  Better one on one, marginally more difficult to follow when he is at the board than his partner. 253.  Myles was always nice, helpful, and patient. He would explain things very well and in different ways until I understood a concept. 255.  Myles was easy to follow on the screen, though sometimes he would type something and then immediately switch to another window on the screen so we couldn't see what it was that he typed. Not a major problem though. 256.  very good with explaining rather than simply giving the answer, handles the stress of a hands on class well 258.  Great TA. 262.  He is phenomenal with debugging code, quick and efficient. 263.  Never met him. 270.  N/A 282.  N/A 283.  Very knowledgeable and presented well. 285.  Miles knew the material very well and was very helpful. 287.  Very smart 288.  Myles is really good at telling us what will work and what would be a waste of time. 289.  Whether or not this is true, it felt like Myles was more knowledgeable on MATLAB than Matt; however, he did not seem like he was as good at the presentation part of teaching as Matt. This made the two of them a pretty solid teaching team, each able to pick up where the other lacked. 290.  Was very good in the help sessions, and the few times he led lectures. 292.  Myles is really nice. 297.  He's an awesome TA! 299.  Myles did a good job of writing out the matlab code and was very knowledgable about coding matlab. 302.  Very helpful and ready to give advice. Maybe could have presented the material more thoroughly, but other than that excellent. 312.  Myles really seemed to know his stuff too. Great TA. He helped a lot. 316.  I received help from Myles at one help session, and he it was super helpful and helped me work out a lot of the little problems with my code. 319.  Looks like Peter Parker. 320.  Met him in help sessions. Knew what he was doing and was very helpful. 321.  While he didn't present for our class, Myles was at several of the help sessions and was by far the best equipped and most willing to explain. Very helpful! 323.  knows his stuff 325.  Didn't have as a TA and only saw at one help session.

Resources

Rate the overall quality of the EF 230 web site.

43% (49/115) Very good (1) 40% (46/115) Good (2) 16% (18/115) Average (3) 2% (2/115) Marginal (4) 0% (0/115) Poor (5) 0% (0/115) N/A (0) Avg: 1.77, NZAvg: 1.77, sum=203, cnt=115, nzcnt=115

General comments/suggestions on web site:

212.  The website is very simple, but very useful in my opinion. It is extremely convenient because it puts everything I need for this class in one place. 214.  I like it, and you should continue using it! It is very helpful and resourceful. 215.  It looks so much different from the EF website I was used to 216.  Spruce it up a bit, like the other websites. Also, it's hard to locate some things on it. 217.  I enjoy the website quite a lot. It's nice to have all the link organized the way the ef site is. 219.  very organized 220.  I think the website is great! 221.  I personally preferred the EF website's setup last academic year (2012-2013) but the website works just fine and is just as easy to use 223.  N/A 224.  The sidebar with links is quite helpful, though some of the links cause unnecessary clutter. 225.  There needs to be a picture of a dragon. Also... In the in-class examples page, including descriptions of each program might help. Including topics covered, functions used, and purpose. 227.  Its easy to get to everything and find what I am looking for. The website is good. 228.  None really, the website has pretty much anything you could need and it is also very user friendly. 229.  The website is fairly clean and straight forward. 230.  I like the way the website is organized and I can find exactly what I am looking for. 232.  Somewhat confusing at points. Due dates are often mixed up. 233.  Should have error signs next to the links that needs tasks to be completed soon. 235.  The discussion board was not used as much as it was in the previous ef and that could be really helpful. 236.  Make sure it is up to date, with the correct dates and years for assignments. 237.  No improvements. Easy to navigate. 238.  Cannot navigate it at all on mobile cause for some reason I couldn't scroll 240.  Set up well and easy to navigate. 243.  It works well, very simple and organized. 244.  The website is a pretty good site for a class such as this. 245.  very user friendly 246.  The website is not very clear when searching for certain subjects in the lab. 247.  I liked the old format 248.  Learned a lot of material that will be helpful in other class. 249.  This is my favorite class website I have seen at the university. If every class was updated like this one I would be less stress out. 250.  The grades page seemed to have been incorrect occasionally, and the running average displayed should not include assignments that are not due yet. 253.  It is hard to go back and learn things from the last few labs we have when I read through the website. It makes me feel that if you don't pay attention to every little detail in class, it is very hard to go back and completely understand the site. 255.  The website was awesome. 256.  very functional on all devices 257.  Website is good, wouldn't change anything 258.  N/A 259.  The website is easy to navigate and its layout is well organized. 260.  Website was fine. I did like the new menu option, it made viewing the lab so much easier. 261.  i dont like the look of new site. i do like the hide menu option though. 262.  The web site functions as it should, I don't see a need to change anything. 263.  well done 264.  send email regarding due dates and such 267.  It works fine. 268.  The in class example aren't very useful compared to what you need to know. 269.  I like the new tablet friendly format 270.  I preferred the 105 website but I got used to this one, so it's probably just because I was used to the 105 site in the first place. 271.  The website is set up very well. It's simple and easy to use and you can get to the page you need in less than 3 clicks usually. 272.  If there was a little more detail maybe or explanation actually explaining what the help file is saying would be awesome. We like the way you guys teach, not the helpfile, it can be confusing at times. 273.  search bar that searches entire website, not just specific locations. 275.  The website is layed out nicely and explains code well. 276.  enjoy the simplicity of the website. I do not personally feel like a visual overhaul would really be necessary for this type of website. 278.  The website was very easy to navigate and easy to use. All in all, it worked perfectly for what was needed of it. 279.  Layout is ok. 281.  Like the website layout. Intuitive. 282.  Website is good, easy to navigate, mobile friendly, and was a good source of help. No changes recommended. 283.  At first I didn't like the change from the regular ef website but having a menu that can go away is extremely useful when you are short on screen space. 284.  very well structured site 285.  Website is set up very well. 286.  Love the interface. Everything is well organized 287.  It's kinda plain and boring 288.  Let students edit the grade sheet so that they can see what grade is needed to earn a certain letter grade. 289.  It got the job done. 290.  Just as expected, no problems and easy to navigate. 291.  I like how you guys made it more accessible from mobile devices. It really helps when I am on the run and trying to see what I need to do for the class. 292.  I definitely like the new lay out. 293.  Easy to navigate and use. Great site 294.  simple, well organized, 295.  The web site is great! Full of information and a good source. 296.  Make it run better on mobile devices. 297.  I like turtles 298.  I had no major issues. Everything on the site was pretty self explanatory. I would not recommend any changes. 299.  The website is good as always. 300.  Examples are slightly more complicated than they need to be. In-class examples were much better. 301.  I think it is very functional and easy to use. 302.  The in-class examples and m-files sections were really useful. 303.  Nothing, it is pretty streamlined, but I don't like that you have to expand the page again when you return to the page from an example. 304.  I like the website, straight to the point. I kind of liked the website for the 2012-2013 year. Wasn't as plain as this one. More appealing. 305.  I wish the website would be updated with more regularity. 306.  The website was well laid out and made coursework easy to access. 308.  Like it. 309.  I wished that the labs and homeworks would have been open from the beginning. 310.  It works well. 311.  Everything we need to know for the homework is on the EF 230 website. Especially the in class sample problems. But I wish there were more useful information on the website for the projects. Basically, we have to learn everything on our own for the projects. They are time consuming and very difficult. 313.  Very well organized, lots of the sidebar links are unnecessary, but the bar can be hidden easily and its not a big problem at all 314.  The website was very well organized and proved helpful. 315.  Very bland. 316.  Well organized and helpful 318.  Very well laid out and accessible. 319.  Messy and jumbled at times in the labs. Every lab is structured in the same way. There are no "steps". If the labs taught us how to use the code step by step(instead of an intro then a full fledged problem) the information would be learned more efficiently. 320.  Needs color. The website has plenty of material although some of it can be confusing. 321.  easy to navigate.. could have used some further introduction to the resources at the begining of the class (m-file search, etc) 323.  n/a 325.  Direct and to the point usually. I know MATLAB like most computer or programming related languages have a ton of information and it can be hard to condense everything that is needed to know in a 2 hour class.

What are your thoughts on a textbook for this class?

3% (3/115) I would purchase a textbook if required (0) 11% (13/115) I would purchase a textbook if recommended (1) 86% (99/115) I don't think a textbook is needed (2) Avg: 1.83, NZAvg: 1.88, sum=211, cnt=115, nzcnt=112

What are your thoughts on using Zyante for the first part of this class?

43% (50/115) I would recommend it (0) 32% (37/115) I would not recommend it (1) 24% (28/115) I don't think it matters either way (2) Avg: 0.81, NZAvg: 1.43, sum=93, cnt=115, nzcnt=65

Are there any other resources that you think might be useful as a formal part of this class?

212.  It would be useful to see more solutions to problems that relate directly to the projects. 214.  None that I can think of. 215.  N/A 216.  N/A 217.  None that I could think of; other than websites from Matlab on codes. 218.  I think the only resource I can think of that the website does not contain would be Zyante. It helped me understand the meaning behind the code. 219.  no I think the website provides enough for the class 220.  No 221.  I think either having a textbook or using Zyante would be a helpful way to go back and view specific examples of the topics being covered. 223.  A textbook would be EXTREMELY useful, as it would allow us to have a paper-reference to use if we end up using matlab later on in life, instead of having to come back and look at the EF website. 224.  None that I am aware of. 225.  Nope. 227.  Zyante was nice to have but for me it was hard for me to follow the book and it gave a lot of info that was not needed. I feel if the labs and the TAs gave all the info we needed I don't think we need to have a textbook. 228.  Zyante or some sort of textbook to where you can go further in depth or find further explanation on a topic that you might not understand. 229.  I think it would be really helpful to have exact examples of how to do homework and projects. I understand it is a conflict of interest to provide exact work but my greatest struggle in this class was often having no working concept of how to approach or complete a project or homework and having no usable example to reference. Yes, there were comparable or similar examples for assignments but nothing that I could directly follow from start to finish. Having atleast one example like this would have helped immensely. And also, it's not as if someone can just copy and paste the work, obviously, so I think having these working examples would be a great way to guide students and help those of us that are extra lost. 230.  Any other website that would aid in using Matlab. 232.  N/A 233.  More help sessions. 234.  Maybe implementing Arduino's to make the class more hands on and interesting 235.  no 236.  Have more of a lecture and lab type class. Just showing me what the code does is helpful, but it makes it easier if we spent more time explaining the logic and reasoning behind some of the things we learn. We need to have time for learning the code and writing/utilizing it. For example, I know how to integrate and I know there's a MatLab command for that. Explain how the specific command works and what it is actually doing. Sometimes stepping through the program helps, but other times it doesn't. Adding more comments on some the code on the website would be helpful too. 237.  n/a 238.  Not really Zyante was just a distraction from actual coding. 240.  N/A 241.  N/A 243.  Not sure what, but I wish there were better resources than matlab help and having to wait for a response on the discussion board. 244.  Not really. 245.  no 246.  The website needs to include by more notes. 248.  N/A 249.  If it is possible, 2 TA's instead of one at help sessions. 253.  Having the students look over the MATLAB help file when dealing with a function. Walking us through those files would help. (I always look at those files anyway, but sometimes I'm not sure about something it is sayings so having a TA walk us through important commands would be helpful). 254.  Not that I can think of. 255.  I thought Zyante did an awesome job. 256.  help session before test 257.  No. 258.  N/A 260.  No 261.  it was helpful i guess... 262.  Maybe one help session per week, even during the weeks when projects aren't being worked on. Possibly for things along the lines of homework or test prep. 263.  if there was another website that explained things a little more in depth. 268.  More homework help towards the end of the semester. 269.  none that I can think of 270.  I think more thorough notes would be a lot more helpful. 271.  I think that the class should have a recommendation for a book that we could use. 272.  Youtube videos if there is time? 273.  More organized help sessions, not just around project due dates. 276.  www.google.com 278.  None that I can think of. 279.  Not that I am aware off. 280.  No. 281.  None except above listed. 282.  283.  Allowing typed notes on test. 284.  more explanation from scheleter 285.  Zyante was good, but it involved too much reading for the pace that this class goes. 286.  No 287.  matlab for a mac 289.  Not really. In high school I took a computer science class and we used a book called "A Gentle Introduction to Object Oriented Programming" with Karel J. Robot. It was a nice way to learn programming, but I don't know if there's anything like that for MATLAB. 290.  Other than a textbook I can't think of anything. However, for the amount of time and depth that this course goes into on each subject I don't believe that a textbook is very necessary. 291.  No, I just think the lectures and the attached .m files given to us after the lectures are good enough. 292.  I really liked the Zyante, especially because it helped out my homework grade. 293.  None. 294.  more links to the mathworks website 296.  go more in depth on explanations of topics in the lab section of this website. 297.  No 298.  I would have like to have had a reference text or a recommended text. I feel it would have helped. There were times where the in class examples and the math works help were confusing. A text may have been able to point me in the right direction. 299.  I think Zyante should be used again, possibly more. 300.  None. 301.  None. 302.  Nope, not that I know of. 303.  No. 304.  Not really. 305.  I don't know of any other resources that I think would be useful. 306.  The internet is usually the best resource for classes like this. I think the class did a good job in teaching us about how the use the mat lab site. 309.  None that I can think of. 310.  I don't know of any. 311.  Make the projects easier or give more lectures on the projects. I learned basic knowledge about MATLAB but the projects were way too difficult. 313.  More videos 314.  No 318.  Not that come to mind. 320.  Nope. The resources provided are useful. 321.  Good for general concepts, that's about it. 322.  Just a comment on Zyante. It is very hard to actually measure how much is learned though it and it can be unnecessarily technical. 323.  n/a 325.  The Phet website was great for ideas if you are thinking about continuing with the same final project.